projects / xen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 447e708) | patch
More details on ordering and safety of the Xen timer API.
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Thu, 9 Feb 2006 11:17:35 +0000 (12:17 +0100)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Thu, 9 Feb 2006 11:17:35 +0000 (12:17 +0100)
commit1fe5f9e97e58fc107f245199307f39fd681c60f1
tree898cca273fa234016d0a783183b5be58d0558edctree | snapshot
parent447e70804785b5a0c7bf519307f0037604bdc55ecommit | diff
More details on ordering and safety of the Xen timer API.
Most functions are safe to call after a timer structure
has been initialised to all zeroes, as long as they are
*never* called concurrently with init_timer().

Signed-off-by: Keir Fraser <keir@xensource.com>
xen/include/xen/timer.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.